Finding ID | Version | Rule ID | IA Controls | Severity |
---|---|---|---|---|
V-241619 | VROM-TC-000255 | SV-241619r879568_rule | Medium |
Description |
---|
After a security incident has occurred, investigators will often review log files to determine what happened. tc Server HORIZON must create a log entry when a user accesses the system and the system authenticates users. The logs must contain information about user sessions to include what type of event occurred, when (date and time) events occurred, where within the server the events occurred, the client source of the events, the outcome (success or failure) of the event, the identity of the user/subject/process associated with the event. As a Tomcat derivative, tc Server can be configured with an “AccessLogValve”. A Valve element represents a component that can be inserted into the request processing pipeline. The pattern attribute of the “AccessLogValve” controls which data gets logged. The “%u” parameter will record the remote user that was authenticated. Knowing the authenticated user could be crucial to know in an investigation. |
STIG | Date |
---|---|
VMware vRealize Operations Manager 6.x tc Server Security Technical Implementation Guide | 2023-09-12 |
Check Text ( C-44895r683717_chk ) |
---|
At the command prompt, execute the following command: tail /storage/log/vcops/log/suite-api/localhost_access_log.YYYY-MM-dd.txt Note: Substitute the actual date in the file name. If the identity of the user is not being recorded, this is a finding. |
Fix Text (F-44854r683718_fix) |
---|
Navigate to and open /usr/lib/vmware-vcops/tomcat-enterprise/conf/server.xml. Navigate to and locate Configure the Note: The “AccessLogValve” should be configured as follows: pattern="%h %l %u %t "%r" %s %b" prefix="localhost_access_log." suffix=".txt"/> |